SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Virtualization</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Virtualization</span></span>

</h1>

</header>

<p>In computing, <b>virtualization</b> (abbreviated <b>v12n</b>) is a series of technologies that allows dividing of physical computing resources into a series of <a href="Virtual_machine" title="Virtual machine">virtual machines</a>, <a href="Operating_system" title="Operating system">operating systems</a>, processes or containers.<sup id="cite_ref-:1_1-0" class="reference"><a href="#cite_note-:1-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

Virtualization began in the 1960s with IBM <a href="CP/CMS" title="CP/CMS">CP/CMS</a>.<sup id="cite_ref-:1_1-1" class="reference"><a href="#cite_note-:1-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> The control program CP provided each user with a simulated stand-alone System/360 computer.

</p><p>In <a href="Hardware_virtualization" title="Hardware virtualization">hardware virtualization</a>, the <i><a href="Host_machine" class="mw-redirect" title="Host machine">host machine</a></i> is the machine that is used by the virtualization and the <i>guest machine</i> is the virtual machine. The words <i>host</i> and <i>guest</i> are used to distinguish the software that runs on the physical machine from the software that runs on the virtual machine. The software or <a href="Firmware" title="Firmware">firmware</a> that creates a virtual machine on the host hardware is called a <i><a href="Hypervisor" title="Hypervisor">hypervisor</a></i> or <i>virtual machine monitor</i>.<sup id="cite_ref-:2_2-0" class="reference"><a href="#cite_note-:2-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> Hardware virtualization is not the same as <a href="Hardware_emulation" title="Hardware emulation">hardware emulation</a>. Hardware-assisted virtualization facilitates building a virtual machine monitor and allows guest OSes to be run in isolation.

</p><p><a href="Desktop_virtualization" title="Desktop virtualization">Desktop virtualization</a> is the concept of separating the <a href="Desktop_environment" title="Desktop environment">logical desktop</a> from the physical machine.

</p><p>Operating-system-level virtualization, also known as <a href="Containerization_(computing)" title="Containerization (computing)">containerization</a>, refers to an <a href="Operating_system" title="Operating system">operating system</a> feature in which the <a href="Kernel_(computer_science)" class="mw-redirect" title="Kernel (computer science)">kernel</a> allows the existence of multiple isolated <a href="User-space" class="mw-redirect" title="User-space">user-space</a> instances.

</p><p>The usual goal of virtualization is to centralize administrative tasks while improving <a href="Scalability" title="Scalability">scalability</a> and overall hardware-resource utilization.

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>A form of virtualization was first demonstrated with IBM's <a href="IBM_CP-40" title="IBM CP-40">CP-40</a> research system in 1967, then distributed via <a href="Open_source" title="Open source">open source</a> in CP/CMS in 1967–1972, and re-implemented in IBM's <a href="VM_(operating_system)" title="VM (operating system)">VM family</a> from 1972 to the present. Each CP/CMS user was provided a simulated, stand-alone computer. Each such virtual machine had the complete capabilities of the underlying machine, and (for its user) the virtual machine was indistinguishable from a private system. This simulation was comprehensive, and was based on the <i>Principles of Operation</i> manual for the hardware. It thus included such elements as an instruction set, main memory, interrupts, exceptions, and device access. The result was a single machine that could be <a href="Multiplexed" class="mw-redirect" title="Multiplexed">multiplexed</a> among many users.

</p><p>Hardware-assisted virtualization first appeared on the <a href="IBM_System/370" title="IBM System/370">IBM System/370</a> in 1972, for use with <a href="VM_(operating_system)" title="VM (operating system)">VM/370</a>, the first virtual machine operating system. IBM added virtual memory hardware to the System/370 series in 1972 which is not the same as Intel VT-x Rings providing a higher privilege level for Hypervisor to properly control Virtual Machines requiring full access to Supervisor and Program or User modes.

</p><p>With the increasing demand for high-definition computer graphics (e.g. <a href="Computer-aided_design" title="Computer-aided design">CAD</a>), virtualization of mainframes lost some attention in the late 1970s, when the upcoming <a href="Minicomputer" title="Minicomputer">minicomputers</a> fostered resource allocation through <a href="Distributed_computing" title="Distributed computing">distributed computing</a>, encompassing the commoditization of <a href="Microcomputer" title="Microcomputer">microcomputers</a>.

</p><p>The increase in compute capacity per x86 server (and in particular the substantial increase in modern networks' bandwidths) rekindled interest in data-center based computing which is based on virtualization techniques. The primary driver was the potential for server consolidation: virtualization allowed a single server to cost-efficiently consolidate compute power on multiple underutilized dedicated servers. The most visible hallmark of a return to the roots of computing is <a href="Cloud_computing" title="Cloud computing">cloud computing</a>, which is a synonym for data center based computing (or mainframe-like computing) through high bandwidth networks. It is closely connected to virtualization.

</p><p>The initial implementation x86 architecture did not meet the <a href="Popek_and_Goldberg_virtualization_requirements" title="Popek and Goldberg virtualization requirements">Popek and Goldberg virtualization requirements</a> to achieve "classical virtualization":

</p>

<ul><li><b>equivalence</b>: a program running under the <a href="Hypervisor" title="Hypervisor">virtual machine monitor (VMM)</a> should exhibit a behavior essentially identical to that demonstrated when running on an equivalent machine directly</li>

<li><b>resource control</b> (also called <b>safety</b>): the VMM must be in complete control of the virtualized resources</li>

<li><b>efficiency</b>: a statistically dominant fraction of machine instructions must be executed without VMM intervention</li></ul>

<p>This made it difficult to implement a virtual machine monitor for this type of processor. Specific limitations included the inability to <a href="Trap_(computing)" class="mw-redirect" title="Trap (computing)">trap</a> on some <a href="Privilege_(computing)" title="Privilege (computing)">privileged</a> instructions.<sup id="cite_ref-Adams_3-0" class="reference"><a href="#cite_note-Adams-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> Therefore, to compensate for these architectural limitations, designers accomplished virtualization of the x86 architecture through two methods: <b>full virtualization</b> or <b>paravirtualization</b>.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> Both create the illusion of physical hardware to achieve the goal of operating system independence from the hardware but present some trade-offs in performance and complexity.

</p><p>Full virtualization was not fully available on the x86 platform prior to 2005. Many <a href="Comparison_of_platform_virtualization_software" title="Comparison of platform virtualization software">platform hypervisors</a> for the x86 platform came very close and claimed full virtualization (such as <a href="Adaptive_Domain_Environment_for_Operating_Systems" title="Adaptive Domain Environment for Operating Systems">Adeos</a>, Mac-on-Linux, <a href="Parallels_Desktop_for_Mac" title="Parallels Desktop for Mac">Parallels Desktop for Mac</a>, <a href="Parallels_Workstation" title="Parallels Workstation">Parallels Workstation</a>, <a href="VMware_Workstation" title="VMware Workstation">VMware Workstation</a>, <a href="VMware_Server" title="VMware Server">VMware Server</a> (formerly GSX Server), <a href="VirtualBox" title="VirtualBox">VirtualBox</a>, Win4BSD, and <a href="Win4Lin" title="Win4Lin">Win4Lin Pro</a>).

</p><p>In 2005 and 2006, <a href="Intel" title="Intel">Intel</a> and <a href="AMD" title="AMD">AMD</a> (working independently) created new processor extensions to the <a href="X86_virtualization#AMD_virtualization_(AMD-V)" title="X86 virtualization">x86 architecture</a> called Intel VT-x and AMD-V, respectively. On the <a href="Itanium" title="Itanium">Itanium</a> architecture, hardware-assisted virtualization is known as VT-i. The first generation of x86 processors to support these extensions were released in late 2005 early 2006:

</p>

<ul><li>On November 13, 2005, Intel released two models of Pentium 4 (Model 662 and 672) as the first Intel processors to support VT-x.</li>

<li>On May 23, 2006, AMD released the Athlon 64 ("Orleans"), the Athlon 64 X2 ("Windsor") and the Athlon 64 FX ("Windsor") as the first <a href="AMD" title="AMD">AMD</a> processors to support this technology.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Hardware_virtualization">Hardware virtualization</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Hardware_virtualization" title="Hardware virtualization">Hardware virtualization</a></div><p><i>Hardware virtualization</i> (or <i>platform virtualization)</i> pools computing resources across one or more <a href="Virtual_machine" title="Virtual machine">virtual machines</a>. A virtual machine implements functionality of a (physical) computer with an operating system. The software or <a href="Firmware" title="Firmware">firmware</a> that creates a virtual machine on the host hardware is called a <i><a href="Hypervisor" title="Hypervisor">hypervisor</a></i> or <i>virtual machine monitor</i>.<sup id="cite_ref-:2_2-1" class="reference"><a href="#cite_note-:2-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p><p>Software executed on these virtual machines is separated from the underlying hardware resources. For example, a computer that is running <a href="Arch_Linux" title="Arch Linux">Arch Linux</a> may host a virtual machine that looks like a computer with the <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> operating system; Windows-based software can be run on the virtual machine.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p><p>Different types of hardware virtualization include:

</p>

<ul><li><b>Full virtualization</b> – Almost complete virtualization of the actual hardware to allow software environments, including a guest operating system and its apps, to run unmodified.</li>

<li><b>Paravirtualization</b> – The guest apps are executed in their own isolated domains, as if they are running on a separate system, but a hardware environment is not simulated. Guest programs need to be specifically modified to run in this environment.</li>

<li><b>Hybrid virtualization</b> – Mostly full virtualization but utilizes paravirtualization drivers to increase <a href="Virtual_machine" title="Virtual machine">virtual machine</a> performance.</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Full_virtualization">Full virtualization</h3></div>

<p>Full virtualization employs techniques that pools physical computer resources into one or more instances; each running a virtual environment where any software or operating system capable of execution on the raw hardware can be run in the virtual machine. Two common full virtualization techniques are typically used: (a) binary translation and (b) hardware-assisted full virtualization.<sup id="cite_ref-:1_1-2" class="reference"><a href="#cite_note-:1-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> Binary translation automatically modifies the software on-the-fly to replace instructions that "pierce the virtual machine" with a different, virtual machine safe sequence of instructions.<sup id="cite_ref-VMware_Paper_7-0" class="reference"><a href="#cite_note-VMware_Paper-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> Hardware-assisted virtualization allows guest operating systems to be run in isolation with virtually no modification to the (guest) operating system.

</p><p>Full virtualization requires that every salient feature of the hardware be reflected into one of several virtual machines – including the full instruction set, <a href="Input/output" title="Input/output">input/output</a> operations, interrupts, memory access, and whatever other elements are used by the software that runs on the <a href="Bare_machine" title="Bare machine">bare machine</a>, and that is intended to run in a virtual machine.

</p><p>This approach was pioneered in 1966 with the IBM <a href="CP-40" class="mw-redirect" title="CP-40">CP-40</a> and <a href="CP-67" title="CP-67">CP-67</a>, predecessors of the <a href="VM_(Operating_system)" class="mw-redirect" title="VM (Operating system)">VM</a> family.

</p>

<div class="mw-heading mw-heading4"><h4 id="Binary_translation">Binary translation</h4></div>

<p>In <a href="Binary_translation" title="Binary translation">binary translation</a>, instructions are translated to match the emulated hardware architecture, if the virtual machine implements a different <a href="Instruction_set_architecture" title="Instruction set architecture">instruction set architecture</a> from that of the hardware on which the virtual machine is being run, or to allow the <a href="Hypervisor" title="Hypervisor">hypervisor</a> to catch hardware references that it must emulate, if the virtual machine implements the same instruction set architecture as the hardware on which the virtual machine is being run.<sup id="cite_ref-:1_1-3" class="reference"><a href="#cite_note-:1-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> The hypervisor, in this case, translates (if emulating a different instruction set architecture) instructions, or replaces (if emulating the host architecture) some OS instructions with safer equivalents, during runtime. On the other hand, in hardware-assisted virtualization, the hypervisor configures the CPU to use the hardware's virtualization mechanism. Furthermore, a hypervisor is not the same as an <a href="Emulator" title="Emulator">emulator</a>; both are computer programs that imitate hardware, but their domain of use in language differs.<sup id="cite_ref-:0_8-0" class="reference"><a href="#cite_note-:0-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading4"><h4 id="Hardware-assisted">Hardware-assisted</h4></div>

<p>Hardware-assisted virtualization (or <i>accelerated virtualization; <a href="Xen" title="Xen">Xen</a> calls it hardware virtual machine (HVM), and <a href="Virtual_Iron" title="Virtual Iron">Virtual Iron</a> calls it native virtualization)</i> is a way of improving overall efficiency of hardware virtualization using help from the host processors. A full virtualization is used to emulate a complete hardware environment, or <a href="Virtual_machine" title="Virtual machine">virtual machine</a>, in which an unmodified guest <a href="Operating_system" title="Operating system">operating system</a> (using the same <a href="Instruction_set" class="mw-redirect" title="Instruction set">instruction set</a> as the host machine) effectively executes in complete isolation.

</p><p>Hardware-assisted virtualization was first introduced on the <a href="IBM_308X" title="IBM 308X">IBM 308X</a> processors in 1980, with the Start Interpretive Execution (SIE) instruction.<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> It was added to <a href="X86" title="X86">x86</a> processors (<a href="Intel_VT-x" class="mw-redirect" title="Intel VT-x">Intel VT-x</a>, <a href="AMD-V" class="mw-redirect" title="AMD-V">AMD-V</a> or <a href="VIA_Technologies" title="VIA Technologies">VIA VT</a>) in 2005, 2006 and 2010<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> respectively.

</p><p><a href="IBM" title="IBM">IBM</a> offers <a href="Hardware_virtualization" title="Hardware virtualization">hardware virtualization</a> for its <a href="IBM_Power_Systems" title="IBM Power Systems">IBM Power Systems</a> hardware for <a href="AIX" class="mw-redirect" title="AIX">AIX</a>, <a href="Linux" title="Linux">Linux</a> and <a href="IBM_i" title="IBM i">IBM i</a>, and for its <a href="IBM_Z" title="IBM Z">IBM Z</a> <a href="Mainframe_computer" title="Mainframe computer">mainframes</a>. IBM refers to its specific form of hardware virtualization as "logical partition", or more commonly as <a href="LPAR" class="mw-redirect" title="LPAR">LPAR</a>.

</p><p>Hardware-assisted virtualization reduces the maintenance overhead of binary translation based virtualization as it reduces (ideally, eliminates) the code that needs to be translated in the guest operating system. It is also considerably easier to obtain better performance.

</p>

<div class="mw-heading mw-heading3"><h3 id="Paravirtualization">Paravirtualization</h3></div>

<p>Paravirtualization is a virtualization technique that presents a software interface to the <a href="Virtual_machine" title="Virtual machine">virtual machines</a> which is similar, yet not identical, to the underlying hardware–software interface. Paravirtualization improves performance and efficiency, compared to full virtualization, by having the guest operating system communicate with the hypervisor. By allowing the guest operating system to indicate its intent to the hypervisor, each can cooperate to obtain better performance when running in a virtual machine.

</p><p>The intent of the modified interface is to reduce the portion of the guest's execution time spent performing operations which are substantially more difficult to run in a virtual environment compared to a non-virtualized environment. The paravirtualization provides specially defined 'hooks' to allow the guest(s) and host to request and acknowledge these tasks, which would otherwise be executed in the virtual domain (where execution performance is worse). A successful paravirtualized platform may allow the <a href="Virtual_machine_monitor" class="mw-redirect" title="Virtual machine monitor">virtual machine monitor</a> (VMM) to be simpler (by relocating execution of critical tasks from the virtual domain to the host domain), and/or reduce the overall performance degradation of machine execution inside the virtual guest.

</p><p>Paravirtualization requires the guest <a href="Operating_system" title="Operating system">operating system</a> to be explicitly <a href="Porting" title="Porting">ported</a> for the para-<a href="Application_programming_interface" class="mw-redirect" title="Application programming interface">API</a> – a conventional OS distribution that is not paravirtualization-aware cannot be run on top of a paravirtualizing VMM. However, even in cases where the operating system cannot be modified, components may be available that enable many of the significant performance advantages of paravirtualization. For example, the Xen Windows GPLPV project provides a kit of paravirtualization-aware device drivers, that are intended to be installed into a <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> virtual guest running on the <a href="Xen" title="Xen">Xen</a> hypervisor.<sup id="cite_ref-XenWindowsGPLPV_11-0" class="reference"><a href="#cite_note-XenWindowsGPLPV-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> Such applications tend to be accessible through the paravirtual machine interface environment. This ensures run-mode compatibility across multiple encryption algorithm models, allowing seamless integration within the paravirtual framework.<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading4"><h4 id="History_2">History</h4></div>

<p>The term "paravirtualization" was first used in the research literature in association with the <a href="Denali_(operating_system)" title="Denali (operating system)">Denali</a> Virtual Machine Manager.<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> The term is also used to describe the <a href="Xen" title="Xen">Xen</a>, <a href="L4_microkernel_family" title="L4 microkernel family">L4</a>, <a href="Trango_Virtual_Processors" title="Trango Virtual Processors">TRANGO</a>, <a href="VMware" title="VMware">VMware</a>, <a href="Wind_River_Systems" title="Wind River Systems">Wind River</a> and <a href="XtratuM" title="XtratuM">XtratuM</a> <a href="Hypervisor" title="Hypervisor">hypervisors</a>. All these projects use or can use paravirtualization techniques to support high performance virtual machines on <a href="X86" title="X86">x86</a> hardware by implementing a virtual machine that does not implement the hard-to-virtualize parts of the actual x86 instruction set.<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup>

</p><p>In 2005, VMware proposed a paravirtualization interface, the Virtual Machine Interface (VMI), as a communication mechanism between the guest operating system and the hypervisor. This interface enabled transparent paravirtualization in which a single binary version of the operating system can run either on native hardware or on a hypervisor in paravirtualized mode.

</p><p>The first appearance of paravirtualization support in Linux occurred with the merge of the ppc64 port in 2002,<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup> which supported running Linux as a paravirtualized guest on IBM pSeries (RS/6000) and iSeries (AS/400) hardware.

</p><p>At the USENIX conference in 2006 in <a href="Boston%2C_Massachusetts" class="mw-redirect" title="Boston, Massachusetts">Boston, Massachusetts</a>, a number of Linux development vendors (including IBM, VMware, Xen, and Red Hat) collaborated on an alternative form of paravirtualization, initially developed by the Xen group, called "paravirt-ops".<sup id="cite_ref-xen-pv-ops_16-0" class="reference"><a href="#cite_note-xen-pv-ops-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup> The paravirt-ops code (often shortened to pv-ops) was included in the mainline <a href="Linux_kernel" title="Linux kernel">Linux kernel</a> as of the 2.6.23 version, and provides a hypervisor-agnostic interface between the hypervisor and guest kernels. Distribution support for pv-ops guest kernels appeared starting with Ubuntu 7.04 and RedHat 9. Xen hypervisors based on any 2.6.24 or later kernel support pv-ops guests, as does VMware's Workstation product beginning with version 6.<sup id="cite_ref-vmware-pv-ops_17-0" class="reference"><a href="#cite_note-vmware-pv-ops-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Hybrid_virtualization">Hybrid virtualization</h3></div>

<p>Hybrid virtualization combines full virtualization techniques with paravirtualized drivers to overcome limitations with hardware-assisted full virtualization.<sup id="cite_ref-18" class="reference"><a href="#cite_note-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup>

</p><p>A hardware-assisted full virtualization approach uses an unmodified guest operating system that involves many VM traps producing high CPU overheads limiting scalability and the efficiency of server consolidation.<sup id="cite_ref-19" class="reference"><a href="#cite_note-19"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup> The hybrid virtualization approach overcomes this problem.

</p>

<div class="mw-heading mw-heading2"><h2 id="Desktop_virtualization">Desktop virtualization</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Desktop_virtualization" title="Desktop virtualization">Desktop virtualization</a></div>

<p>Desktop virtualization separates the <a href="Desktop_environment" title="Desktop environment">logical desktop</a> from the physical machine.

</p><p>One form of desktop virtualization, virtual desktop infrastructure (VDI), can be thought of as a more advanced form of hardware virtualization. Rather than interacting with a host computer directly via a keyboard, mouse, and monitor, the user interacts with the host computer using another desktop computer or a mobile device by means of a network connection, such as a <a href="LAN" class="mw-redirect" title="LAN">LAN</a>, <a href="Wireless_LAN" title="Wireless LAN">Wireless LAN</a> or even the <a href="Internet" title="Internet">Internet</a>. In addition, the host computer in this scenario becomes a <a href="Server_computer" class="mw-redirect" title="Server computer">server computer</a> capable of hosting multiple virtual machines at the same time for multiple users.<sup id="cite_ref-consumerization_20-0" class="reference"><a href="#cite_note-consumerization-20"><span class="cite-bracket">[</span>20<span class="cite-bracket">]</span></a></sup>

</p><p>Companies like <a href="Hewlett-Packard" title="Hewlett-Packard">HP</a> and <a href="IBM" title="IBM">IBM</a> provide a hybrid VDI model with a range of virtualization software and delivery models to improve upon the limitations of <a href="Distributed_computing" title="Distributed computing">distributed client computing</a>.<sup id="cite_ref-ZDNet_21-0" class="reference"><a href="#cite_note-ZDNet-21"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup> Selected client environments move workloads from PCs and other devices to data center servers, creating well-managed virtual clients, with applications and client operating environments hosted on servers and storage in the data center. For users, this means they can access their desktop from any location, without being tied to a single client device. Since the resources are centralized, users moving between work locations can still access the same client environment with their applications and data.<sup id="cite_ref-ZDNet_21-1" class="reference"><a href="#cite_note-ZDNet-21"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup> For IT administrators, this means a more centralized, efficient client environment that is easier to maintain and able to more quickly respond to the changing needs of the user and business.<sup id="cite_ref-22" class="reference"><a href="#cite_note-22"><span class="cite-bracket">[</span>22<span class="cite-bracket">]</span></a></sup>

Another form, session virtualization, allows multiple users to connect and <a href="Login" title="Login">log into</a> a shared but powerful computer over the network and use it simultaneously. Each is given a desktop and a personal folder in which they store their files.<sup id="cite_ref-consumerization_20-1" class="reference"><a href="#cite_note-consumerization-20"><span class="cite-bracket">[</span>20<span class="cite-bracket">]</span></a></sup> With <a href="Multiseat_configuration" title="Multiseat configuration">multiseat configuration</a>, session virtualization can be accomplished using a single PC with multiple monitors, keyboards, and mice connected.

</p><p><a href="Thin_client" title="Thin client">Thin clients</a>, which are seen in desktop virtualization, are simple and/or cheap computers that are primarily designed to connect to the network. They may lack significant <a href="Hard_disk_drive" title="Hard disk drive">hard disk storage space</a>, <a href="Random_access_memory" class="mw-redirect" title="Random access memory">RAM</a> or even <a href="Central_processing_unit" title="Central processing unit">processing power</a>, but many organizations are beginning to look at the cost benefits of eliminating "thick client" desktops that are packed with software (and require software licensing fees) and making more strategic investments.<sup id="cite_ref-23" class="reference"><a href="#cite_note-23"><span class="cite-bracket">[</span>23<span class="cite-bracket">]</span></a></sup>

</p><p>Desktop virtualization simplifies software versioning and patch management, where the new image is simply updated on the server, and the desktop gets the updated version when it reboots. It also enables centralized control over what applications the user is allowed to have access to on the workstation.

</p><p>Moving virtualized desktops into the cloud creates hosted virtual desktops (HVDs), in which the desktop images are centrally managed and maintained by a specialist hosting firm. Benefits include scalability and the reduction of capital expenditure, which is replaced by a monthly operational cost.<sup id="cite_ref-24" class="reference"><a href="#cite_note-24"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Containerization">Containerization</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Operating-system-level_virtualization" class="mw-redirect" title="Operating-system-level virtualization">Operating-system-level virtualization</a></div>

<p>Operating-system-level virtualization, also known as <a href="Containerization_(computing)" title="Containerization (computing)">containerization</a>, refers to an <a href="Operating_system" title="Operating system">operating system</a> feature in which the <a href="Kernel_(computer_science)" class="mw-redirect" title="Kernel (computer science)">kernel</a> allows the existence of multiple isolated <a href="User-space" class="mw-redirect" title="User-space">user-space</a> instances. Such instances, called containers,<sup id="cite_ref-25" class="reference"><a href="#cite_note-25"><span class="cite-bracket">[</span>25<span class="cite-bracket">]</span></a></sup> partitions, virtual environments (VEs) or jails (<a href="FreeBSD_jail" title="FreeBSD jail">FreeBSD jail</a> or <a href="Chroot_jail" class="mw-redirect" title="Chroot jail">chroot jail</a>), may look like (physical) computers from the point of view of programs running in them. A computer program running on an ordinary operating system can see all resources (connected devices, files and folders, <a href="Shared_resource" title="Shared resource">network shares</a>, CPU power, quantifiable hardware capabilities) of that computer. However, programs running inside a container can only see the container's contents and devices assigned to the container.

</p><p>This provides many of the benefits that virtual machines have such as standardization and scalability, while using less resources as the kernel is shared between containers.<sup id="cite_ref-26" class="reference"><a href="#cite_note-26"><span class="cite-bracket">[</span>26<span class="cite-bracket">]</span></a></sup>

</p><p>Containerization started gaining prominence in 2014, with the introduction of <a href="Docker_(software)" title="Docker (software)">Docker</a>.<sup id="cite_ref-27" class="reference"><a href="#cite_note-27"><span class="cite-bracket">[</span>27<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-28" class="reference"><a href="#cite_note-28"><span class="cite-bracket">[</span>28<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Miscellaneous_types">Miscellaneous types</h2></div>

<dl><dt>Software</dt></dl>

<ul><li><a href="Application_virtualization" title="Application virtualization">Application virtualization</a> and <a href="Workspace_virtualization" title="Workspace virtualization">workspace virtualization</a>: isolating individual apps from the underlying OS and other apps; closely associated with the concept of <a href="Portable_application" title="Portable application">portable applications</a></li>

<li><a href="Service_virtualization" title="Service virtualization">Service virtualization</a>: emulating the behavior of specific components in heterogeneous component-based applications such as <a href="API" title="API">API</a>-driven applications, <a href="Cloud_computing" title="Cloud computing">cloud</a>-based applications and <a href="Service-oriented_architecture" title="Service-oriented architecture">service-oriented architectures</a></li></ul>

<dl><dt>Memory</dt></dl>

<ul><li><a href="Memory_virtualization" title="Memory virtualization">Memory virtualization</a>: Aggregating RAM resources from multiple networked systems into a <b>single unified memory pool</b> is a concept often referred to as <b>disaggregated memory</b>, <b>memory pooling</b>, or <b>remote memory access</b>. This architecture aims to overcome the traditional memory limitations of a single system by enabling multiple computers or nodes to share their memory in a high-performance, low-latency manner.</li>

<li><a href="Virtual_memory" title="Virtual memory">Virtual memory</a>: giving an app the impression that it has contiguous working memory, isolating it from the underlying physical memory implementation</li></ul>

<dl><dt>Storage</dt></dl>

<ul><li><a href="Storage_virtualization" title="Storage virtualization">Storage virtualization</a>: the process of completely abstracting logical storage from physical storage</li>

<li><a href="Distributed_file_system" class="mw-redirect" title="Distributed file system">Distributed file system</a>: any <a href="File_system" title="File system">file system</a> that allows access to files from multiple hosts sharing via a computer network</li>

<li><a href="Virtual_file_system" title="Virtual file system">Virtual file system</a>: an abstraction layer on top of a more concrete file system, allowing client applications to access different types of concrete file systems in a uniform way</li>

<li><a href="Storage_hypervisor" class="mw-redirect" title="Storage hypervisor">Storage hypervisor</a>: the software that manages storage virtualization and combines physical storage resources into one or more flexible pools of logical storage<sup id="cite_ref-29" class="reference"><a href="#cite_note-29"><span class="cite-bracket">[</span>29<span class="cite-bracket">]</span></a></sup></li>

<li><a href="Virtual_disk" class="mw-redirect" title="Virtual disk">Virtual disk</a>: a computer program that emulates a disk drive such as a <a href="Hard_disk_drive" title="Hard disk drive">hard disk drive</a> or <a href="Optical_disk_drive" class="mw-redirect" title="Optical disk drive">optical disk drive</a> (see <a href="Comparison_of_disc_image_software" title="Comparison of disc image software">comparison of disc image software</a>)</li></ul>

<ul><li><a href="Data_virtualization" title="Data virtualization">Data virtualization</a>: the presentation of data as an abstract layer, independent of underlying database systems, structures and storage</li>

<li><a href="Database_virtualization" title="Database virtualization">Database virtualization</a>: the decoupling of the database layer, which lies between the storage and application layers within the application stack over all</li></ul>

<dl><dt>Network</dt></dl>

<ul><li><a href="Network_virtualization" title="Network virtualization">Network virtualization</a>: creation of a virtualized network <a href="Address_space" title="Address space">addressing space</a> within or across network subnets</li>

<li><a href="Virtual_private_network" title="Virtual private network">Virtual private network</a> (VPN): a <a href="Network_protocol" class="mw-redirect" title="Network protocol">network protocol</a> that replaces the actual wire or other physical media in a network with an abstract layer, allowing a network to be created over the <a href="Internet" title="Internet">Internet</a></li>

<li><a href="Network_Protocol_Virtualization" title="Network Protocol Virtualization">Network Protocol Virtualization</a>: decoupling networking layers in order to accelerate the deployment and management of networks</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Benefits_and_disadvantages">Benefits and disadvantages</h2></div>

<p>Virtualization, in particular, full virtualization has proven beneficial for:

</p>

<ul><li>sharing a computer system among multiple users;</li>

<li>isolating users from each other (and from the control program);</li>

<li>emulating new hardware to achieve improved reliability, security, and productivity.</li></ul>

<p>A common goal of virtualization is to centralize administrative tasks while improving <a href="Scalability" title="Scalability">scalability</a> and overall hardware-resource utilization. With virtualization, several operating systems can be run in parallel on a single <a href="Central_processing_unit" title="Central processing unit">central processing unit</a> (CPU). This parallelism tends to reduce overhead costs and differs from multitasking, which involves running several programs on the same OS. Using virtualization, an enterprise can better manage updates and rapid changes to the operating system and applications without disrupting the user. "

</p><p>Ultimately, virtualization dramatically improves the efficiency and availability of resources and applications in an organization. Instead of relying on the old model of "one server, one application" that leads to underutilized resources, virtual resources are dynamically applied to meet business needs without any excess fat".<sup id="cite_ref-30" class="reference"><a href="#cite_note-30"><span class="cite-bracket">[</span>30<span class="cite-bracket">]</span></a></sup>

</p><p>Virtual machines running proprietary operating systems require licensing, regardless of the host machine's operating system. For example, installing <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> into a VM guest requires its licensing requirements to be satisfied.<sup id="cite_ref-31" class="reference"><a href="#cite_note-31"><span class="cite-bracket">[</span>31<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-32" class="reference"><a href="#cite_note-32"><span class="cite-bracket">[</span>32<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-33" class="reference"><a href="#cite_note-33"><span class="cite-bracket">[</span>33<span class="cite-bracket">]</span></a></sup>

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}

/* end https://en.wikipedia.org/ */

</style><div class="div-col" style="column-width: 25em;">

<ul><li><a href="AI-assisted_virtualization_software" title="AI-assisted virtualization software">AI-assisted virtualization software</a></li>

<li><a href="Timeline_of_virtualization_development" class="mw-redirect" title="Timeline of virtualization development">Timeline of virtualization development</a></li>

<li><a href="Network_function_virtualization" title="Network function virtualization">Network function virtualization</a></li>

<li><a href="Digital_twin" title="Digital twin">Digital twin</a></li>

<li><a href="Emulation_(computing)" class="mw-redirect" title="Emulation (computing)">Emulation (computing)</a></li>

<li><a href="Computer_simulation" title="Computer simulation">Computer simulation</a></li>

<li><a href="Containerization_(computing)" title="Containerization (computing)">Containerization</a></li>

<li><a href="Consolidation_ratio" title="Consolidation ratio">Consolidation ratio</a></li>

<li><a href="I/O_virtualization" title="I/O virtualization">I/O virtualization</a></li>

<li><a href="Application_checkpointing" title="Application checkpointing">Application checkpointing</a></li>

<li><a href="Virtual_art" title="Virtual art">Virtual art</a></li>

<li><a href="OS_virtualization_and_emulation_on_Android" title="OS virtualization and emulation on Android">OS virtualization and emulation on Android</a></li>

<li><a href="Application_virtualization" title="Application virtualization">Application virtualization</a></li>

<li><a href="User_virtualization" title="User virtualization">User virtualization</a></li></ul>

</div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFRodríguez-HaroFreitagNavarroHernánchez-sánchez2012" class="citation journal cs1">Rodríguez-Haro, Fernando; Freitag, Felix; Navarro, Leandro; Hernánchez-sánchez, Efraín; Farías-Mendoza, Nicandro; Guerrero-Ibáñez, Juan Antonio; González-Potes, Apolinar (2012-01-01). <a rel="nofollow" class="external text" href="https://www.sciencedirect.com/science/article/pii/S2212017312002587">"A summary of virtualization techniques"</a>. <i>Procedia Technology</i>. The 2012 Iberoamerican Conference on Electronics Engineering and Computer Science. <b>3</b>: <span class="nowrap">267–</span>272. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.protcy.2012.03.029">10.1016/j.protcy.2012.03.029</a></span>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2212-0173">2212-0173</a>.</cite></span>

</li>

<li id="cite_note-:2-2"><span class="mw-cite-backlink">^ <a href="#cite_ref-:2_2-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:2_2-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFTurbanKingLeeViehland2008" class="citation book cs1">Turban, E; King, D.; Lee, J.; Viehland, D. (2008). "19". <a rel="nofollow" class="external text" href="http://wps.prenhall.com/wps/media/objects/5073/5195381/pdf/Online_Chapter_19.pdf"><i>Electronic Commerce A Managerial Perspective</i></a> <span class="cs1-format">(PDF)</span> (5th ed.). Prentice-Hall. p. 27.</cite></span>

</li>

<li id="cite_note-Adams-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-Adams_3-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFAdams" class="citation web cs1">Adams, Keith. <a rel="nofollow" class="external text" href="http://www.vmware.com/pdf/asplos235_adams.pdf">"A Comparison of Software and Hardware Techniques for x86 Virtualization"</a> <span class="cs1-format">(PDF)</span><span class="reference-accessdate">. Retrieved <span class="nowrap">20 January</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text">Chris Barclay, <i>New approach to virtualizing x86s</i>, <a href="Network_World" class="mw-redirect" title="Network World">Network World</a>, 20 October 2006</span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite id="CITEREFTurbanKingLeeViehland2008" class="citation book cs1">Turban, E; King, D; Lee, J; Viehland, D (2008). "Chapter 19: Building E-Commerce Applications and Infrastructure". <i>Electronic Commerce A Managerial Perspective</i>. Prentice-Hall. p. 27.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www-07.ibm.com/solutions/in/education/download/Virtualization%20in%20Education.pdf">"Virtualization in education"</a> <span class="cs1-format">(PDF)</span>. <a href="IBM" title="IBM">IBM</a>. October 2007<span class="reference-accessdate">. Retrieved <span class="nowrap">6 July</span> 2010</span>. <q>A virtual computer is a logical representation of a computer in software. By decoupling the physical hardware from the operating system, virtualization provides more operational flexibility and increases the utilization rate of the underlying physical hardware.</q></cite></span>

</li>

<li id="cite_note-VMware_Paper-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-VMware_Paper_7-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFVMware2007" class="citation web cs1">VMware (11 Sep 2007). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080511171622/http://www.vmware.com/files/pdf/VMware_paravirtualization.pdf">"Understanding Full Virtualization, Paravirtualization, and Hardware Assist"</a> <span class="cs1-format">(PDF)</span>. <a href="VMware" title="VMware">VMware</a>. Archived from <a rel="nofollow" class="external text" href="https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/VMware_paravirtualization.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2008-05-11<span class="reference-accessdate">. Retrieved <span class="nowrap">2021-05-20</span></span>.</cite></span>

</li>

<li id="cite_note-:0-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-:0_8-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFCreasy1981" class="citation web cs1">Creasy, R.J. (1981). <a rel="nofollow" class="external text" href="http://pages.cs.wisc.edu/~stjones/proj/vm_reading/ibmrd2505M.pdf">"The Origin of the VM/370 Time-sharing System"</a> <span class="cs1-format">(PDF)</span>. <a href="IBM" title="IBM">IBM</a><span class="reference-accessdate">. Retrieved <span class="nowrap">26 February</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite class="citation book cs1"><a rel="nofollow" class="external text" href="http://bitsavers.org/pdf/ibm/370/MVS_XA/SA22-7095-0_370-XA_Interpretive_Execution_Jan84.pdf"><i>IBM System/370 Extended Architecture Interpretive Execution</i></a> <span class="cs1-format">(PDF)</span> (First ed.). IBM. January 1984. SA22-7095-0<span class="reference-accessdate">. Retrieved <span class="nowrap">October 27,</span> 2022</span>.</cite></span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite class="citation pressrelease cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20130122011049/http://www.via.com.tw/en/resources/pressroom/pressrelease.jsp?press_release_no=4247">"VIA Introduces New VIA Nano 3000 Series Processors"</a>. <i>www.via.com.tw</i> (Press release). Archived from <a rel="nofollow" class="external text" href="http://www.via.com.tw/en/resources/pressroom/pressrelease.jsp?press_release_no=4247">the original</a> on 22 January 2013<span class="reference-accessdate">. Retrieved <span class="nowrap">10 October</span> 2022</span>.</cite></span>

</li>

<li id="cite_note-XenWindowsGPLPV-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-XenWindowsGPLPV_11-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers">"Installing signed GPLPV drivers in Windows Xen instances"</a>. <i>Univention Wiki</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2013-04-10</span></span>. <q>The GPLPV driver is a driver for Microsoft Windows, which enables Windows DomU systems virtualised in Xen to access the network and block drivers of the Xen Dom0. This provides a significant performance and reliability gain over the standard devices emulated by Xen/Qemu/Kvm.</q></cite></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><cite id="CITEREFArmstrong2011" class="citation journal cs1">Armstrong, D (2011). "Performance issues in clouds: An evaluation of virtual image propagation and I/O paravirtualization". <i>The Computer Journal</i>. <b>54</b> (6): <span class="nowrap">836–</span>849. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1093%2Fcomjnl%2Fbxr011">10.1093/comjnl/bxr011</a>.</cite></span>

</li>

<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text"><cite id="CITEREFA._WhitakerM._ShawS._D._Gribble2002" class="citation web cs1">A. Whitaker; M. Shaw; S. D. Gribble (2002). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080114003008/http://denali.cs.washington.edu/pubs/index.html">"Denali: Lightweight Virtual Machines for Distributed and Networked Applications"</a>. University of Washington Technical Report. Archived from <a rel="nofollow" class="external text" href="http://denali.cs.washington.edu/pubs/index.html">the original</a> on 2008-01-14<span class="reference-accessdate">. Retrieved <span class="nowrap">2006-12-09</span></span>.</cite></span>

</li>

<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text"><cite id="CITEREFStrobl2013" class="citation book cs1">Strobl, Marius (2013). <a rel="nofollow" class="external text" href="http://www.grin.com/e-book/233001/"><i>Virtualization for Reliable Embedded Systems</i></a>. Munich: GRIN Publishing GmbH. p. 54,63. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-3-656-49071-5</bdi>.</cite></span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text"><cite id="CITEREFAnton_Blanchard" class="citation web cs1">Anton Blanchard. <a rel="nofollow" class="external text" href="https://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux-fullhistory.git/commit/?id=c3aa9878533e724f639852c3d951e6a169e04081">"Add ppc64 support"</a>. <i>kernel.org</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2024-04-24</span></span>.</cite></span>

</li>

<li id="cite_note-xen-pv-ops-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-xen-pv-ops_16-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://wiki.xenproject.org/wiki/XenParavirtOps">"XenParavirtOps – Xen"</a>. <i>Wiki.xenproject.org</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2017-03-03</span></span>.</cite></span>

</li>

<li id="cite_note-vmware-pv-ops-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-vmware-pv-ops_17-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110413042731/http://www.vmware.com/company/news/releases/050907PV.html">"VMware Introduces Support for Cross-Platform Paravirtualization – VMware"</a>. VMware. 16 May 2008. Archived from <a rel="nofollow" class="external text" href="http://www.vmware.com/company/news/releases/050907PV.html">the original</a> on 13 April 2011.</cite></span>

</li>

<li id="cite_note-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-18">^</a></b></span> <span class="reference-text">Jun Nakajima and Asit K. Mallick, <a rel="nofollow" class="external text" href="http://ols.108.redhat.com/2007/Reprints/nakajima-Reprint.pdf">"Hybrid-Virtualization—Enhanced Virtualization for Linux"</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20090107033134/http://ols.108.redhat.com/2007/Reprints/nakajima-Reprint.pdf">Archived</a> 2009-01-07 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, in <i>Proceedings of the Linux Symposium</i>, Ottawa, June 2007.</span>

</li>

<li id="cite_note-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-19">^</a></b></span> <span class="reference-text">See <a rel="nofollow" class="external text" href="http://www.valinux.co.jp/documents/tech/presentlib/2007/2007xenconf/Intel.pdf">"Hybrid Virtualization: The Next Generation of XenLinux"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20090320083020/http://www.valinux.co.jp/documents/tech/presentlib/2007/2007xenconf/Intel.pdf">Archived</a> March 20, 2009, at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>

</li>

<li id="cite_note-consumerization-20"><span class="mw-cite-backlink">^ <a href="#cite_ref-consumerization_20-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-consumerization_20-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110815201911/http://download.microsoft.com/download/E/F/5/EF5F8B95-5E27-4CDB-860F-F982E5B714B0/Strategies%20for%20Embracing%20Consumerization.pdf">"Strategies for Embracing Consumerization"</a> <span class="cs1-format">(PDF)</span>. Microsoft Corporation. April 2011. p. 9. Archived from <a rel="nofollow" class="external text" href="http://download.microsoft.com/download/E/F/5/EF5F8B95-5E27-4CDB-860F-F982E5B714B0/Strategies%20for%20Embracing%20Consumerization.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 15 August 2011<span class="reference-accessdate">. Retrieved <span class="nowrap">22 July</span> 2011</span>.</cite></span>

</li>

<li id="cite_note-ZDNet-21"><span class="mw-cite-backlink">^ <a href="#cite_ref-ZDNet_21-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-ZDNet_21-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFChernicoff2011" class="citation web cs1">Chernicoff, David (August 19, 2011). <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/hp-vdi-moves-to-center-stage/">"HP VDI Moves to Center Stage"</a>. <i><a href="ZDNet" class="mw-redirect" title="ZDNet">ZDNet</a></i>.</cite></span>

</li>

<li id="cite_note-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-22">^</a></b></span> <span class="reference-text"><cite id="CITEREFBaburajan2011" class="citation web cs1">Baburajan, Rajani (August 24, 2011). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120106005032/http://it.tmcnet.com/channels/cloud-storage/articles/211183-rising-cloud-storage-market-opportunity-strengthens-vendors.htm">"The Rising Cloud Storage Market Opportunity Strengthens Vendors"</a>. <i>infoTECH</i>. Archived from <a rel="nofollow" class="external text" href="http://it.tmcnet.com/channels/cloud-storage/articles/211183-rising-cloud-storage-market-opportunity-strengthens-vendors.htm">the original</a> on 2012-01-06<span class="reference-accessdate">. Retrieved <span class="nowrap">2011-08-24</span></span>.</cite></span>

</li>

<li id="cite_note-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-23">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://content.dell.com/us/en/enterprise/d/large-business/desktop-virtualization-place.aspx">"Desktop Virtualization Tries to Find Its Place in the Enterprise"</a>. Dell.com<span class="reference-accessdate">. Retrieved <span class="nowrap">2012-06-19</span></span>.</cite></span>

</li>

<li id="cite_note-24"><span class="mw-cite-backlink"><b><a href="#cite_ref-24">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20121002231021/http://www.intrinsictechnology.co.uk/FileUploads/HVD_Whitepaper.pdf">"HVD: the cloud's silver lining"</a> <span class="cs1-format">(PDF)</span>. Intrinsic Technology. Archived from <a rel="nofollow" class="external text" href="http://www.intrinsictechnology.co.uk/FileUploads/HVD_Whitepaper.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2 October 2012<span class="reference-accessdate">. Retrieved <span class="nowrap">30 August</span> 2012</span>.</cite></span>

</li>

<li id="cite_note-25"><span class="mw-cite-backlink"><b><a href="#cite_ref-25">^</a></b></span> <span class="reference-text"><cite id="CITEREFHogg2014" class="citation web cs1">Hogg, Scott (2014-05-26). <a rel="nofollow" class="external text" href="https://www.networkworld.com/article/749098/cisco-subnet-software-containers-used-more-frequently-than-most-realize.html">"Software Containers: Used More Frequently than Most Realize"</a>. <i>Network World</i>. Network World, Inc<span class="reference-accessdate">. Retrieved <span class="nowrap">2015-07-09</span></span>.</cite></span>

</li>

<li id="cite_note-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-26">^</a></b></span> <span class="reference-text"><cite id="CITEREFGandhi2019" class="citation web cs1">Gandhi, Rajeev (2019-02-06). <a rel="nofollow" class="external text" href="https://www.ibm.com/blog/the-benefits-of-containerization-and-what-it-means-for-you/">"The Benefits of Containerization and What It Means for You"</a>. <i>IBM Blog</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2024-03-15</span></span>.</cite></span>

</li>

<li id="cite_note-27"><span class="mw-cite-backlink"><b><a href="#cite_ref-27">^</a></b></span> <span class="reference-text"><cite id="CITEREFVaughan-Nichols2018" class="citation web cs1">Vaughan-Nichols, Steven J. (21 March 2018). <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/what-is-docker-and-why-is-it-so-darn-popular/">"What is Docker and why is it so darn popular?"</a>. <i><a href="ZDNet" class="mw-redirect" title="ZDNet">ZDNet</a></i>. <a href="CBS_Interactive" class="mw-redirect" title="CBS Interactive">CBS Interactive</a>.</cite></span>

</li>

<li id="cite_note-28"><span class="mw-cite-backlink"><b><a href="#cite_ref-28">^</a></b></span> <span class="reference-text"><cite id="CITEREFButler2014" class="citation web cs1">Butler, Brandon (10 June 2014). <a rel="nofollow" class="external text" href="https://www.networkworld.com/article/925600/cloud-computing-docker-101-what-it-is-and-why-it-s-important.html">"Docker 101: What it is and why it's important"</a>. <i><a href="Network_World" class="mw-redirect" title="Network World">Network World</a></i>. <a href="IDG" class="mw-redirect" title="IDG">IDG</a>.</cite></span>

</li>

<li id="cite_note-29"><span class="mw-cite-backlink"><b><a href="#cite_ref-29">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120330235752/http://www.raido.be/frontend/files/whitepapers/20_j3ykqsmm.pdf">"Enterprise Systems Group White paper, Page 5"</a> <span class="cs1-format">(PDF)</span>. Enterprise Strategy Group White Paper written and published on August 20, 2011 by Mark Peters. Archived from <a rel="nofollow" class="external text" href="http://www.raido.be/frontend/files/whitepapers/20_j3ykqsmm.pdf">the original</a> <span class="cs1-format">(PDF)</span> on March 30, 2012<span class="reference-accessdate">. Retrieved <span class="nowrap">July 18,</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-30"><span class="mw-cite-backlink"><b><a href="#cite_ref-30">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www-07.ibm.com/solutions/in/education/download/Virtualization%20in%20Education.pdf">"Virtualization in education"</a> <span class="cs1-format">(PDF)</span>. <a href="IBM" title="IBM">IBM</a>. October 2007<span class="reference-accessdate">. Retrieved <span class="nowrap">6 July</span> 2010</span>.</cite></span>

</li>

<li id="cite_note-31"><span class="mw-cite-backlink"><b><a href="#cite_ref-31">^</a></b></span> <span class="reference-text"><cite id="CITEREFFoley2012" class="citation web cs1">Foley, Mary Jo (5 July 2012). <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/microsoft-goes-public-with-windows-server-2012-versions-licensing/">"Microsoft goes public with Windows Server 2012 versions, licensing"</a>. <i><a href="ZDNet" class="mw-redirect" title="ZDNet">ZDNet</a></i>. <a href="CBS_Interactive" class="mw-redirect" title="CBS Interactive">CBS Interactive</a>. <q>Finn explained that Standard covers 2 CPUs in a host, and goes from one VOSE (virtual operating system environment - 1 free Std install in a VM on that host) to two, and 'now has all the features and scalability of Datacenter.' He noted there will be a small price increase, but said he thought that wouldn't matter, as it 'should be virtualized anyway and the VOSE rights doubling will compensate. Windows Server Datacenter was a minimum of two 1-CPU licenses with unlimited VOSEs. 'Now it is a simpler SKU that covers two CPUs in a host with unlimited VOSEs,' Finn said.</q></cite></span>

</li>

<li id="cite_note-32"><span class="mw-cite-backlink"><b><a href="#cite_ref-32">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://download.microsoft.com/download/4/D/B/4DB352D1-C610-466A-9AAF-EEF4F4CFFF27/WS2012_Licensing-Pricing_FAQ.pdf">"Windows Server 2012 Licensing and Pricing FAQ"</a> <span class="cs1-format">(PDF)</span>. Microsoft<span class="reference-accessdate">. Retrieved <span class="nowrap">5 July</span> 2012</span>.</cite></span>

</li>

<li id="cite_note-33"><span class="mw-cite-backlink"><b><a href="#cite_ref-33">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://download.microsoft.com/download/9/8/d/98d6a56c-4d79-40f4-8462-da3ecba2dc2c/licensing_windows_desktop_os_for_virtual_machines.pdf">"Licensing Windows desktop operating system for use with virtual machines"</a> <span class="cs1-format">(PDF)</span>. <i>microsoft.com</i>. <a href="Microsoft" title="Microsoft">Microsoft</a><span class="reference-accessdate">. Retrieved <span class="nowrap">22 December</span> 2018</span>.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Look up <i><b><a href="https://en.wiktionary.org/wiki/Special:Search/virtualization" class="extiw external" title="wiktionary:Special:Search/virtualization">virtualization</a></b></i> in Wiktionary, the free dictionary.</div></div>

</div>

<div class="side-box-text plainlist">Wikimedia Commons has media related to <span style="font-weight: bold; font-style: italic;"><a href="https://commons.wikimedia.org/wiki/Category:Virtualization" class="extiw external" title="commons:Category:Virtualization">Virtualization</a></span>.</div></div>

</div>

<ul><li><a rel="nofollow" class="external text" href="https://webx.ubi.pt/~hgil/utils/Virtualization_Introduction.html">An Introduction to Virtualization</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201022004035/https://webx.ubi.pt/~hgil/utils/Virtualization_Introduction.html">Archived</a> 2020-10-22 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, January 2004, by Amit Singh</li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Virtualization_software371" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Virtualization_software371" style="font-size:114%;margin:0 4em"> software</div></th></tr><tr><td class="navbox-abovebelow" colspan="2"><div><a href="Comparison_of_platform_virtualization_software" title="Comparison of platform virtualization software">Comparison of platform virtualization software</a></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Hardware_virtualization" title="Hardware virtualization">Hardware</a><br>(<a href="Hypervisor" title="Hypervisor">hypervisors</a>)</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Native</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Adaptive_Domain_Environment_for_Operating_Systems" title="Adaptive Domain Environment for Operating Systems">Adeos</a></li>

<li><a href="Hyper-V" title="Hyper-V">Hyper-V</a></li>

<ul><li><a href="OVirt" title="OVirt">oVirt</a></li>

<li>KubeVirt</li></ul></li>

<li><a href="Oracle_VM_Server_for_SPARC" title="Oracle VM Server for SPARC">LDoms / Oracle VM Server for SPARC</a></li>

<li><a href="Logical_partition" title="Logical partition">Logical partition</a> (LPAR)</li>

<li><a href="LynxSecure" title="LynxSecure">LynxSecure</a></li>

<li><a href="PikeOS" title="PikeOS">PikeOS</a></li>

<li><a href="Proxmox_Virtual_Environment" title="Proxmox Virtual Environment">Proxmox VE</a></li>

<li><a href="SIMMON" title="SIMMON">SIMMON</a></li>

<li><a href="VMware_ESXi" title="VMware ESXi">VMware ESXi</a>

<ul><li><a href="VMware_vSphere" title="VMware vSphere">VMware vSphere</a></li>

<li><a href="VCloud_Air" title="VCloud Air">vCloud</a></li></ul></li>

<li><a href="VMware_Infrastructure" title="VMware Infrastructure">VMware Infrastructure</a></li>

<ul><li><a href="XenServer" class="mw-redirect" title="XenServer">XenServer</a></li>

<li><a href="XtratuM" title="XtratuM">XtratuM</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Hosted</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Specialized</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Basilisk_II" title="Basilisk II">Basilisk II</a></li>

<li><a href="Bochs" title="Bochs">Bochs</a></li>

<li><a href="Cooperative_Linux" title="Cooperative Linux">Cooperative Linux</a></li>

<li><a href="DOSBox" title="DOSBox">DOSBox</a></li>

<li><a href="DOSEMU" title="DOSEMU">DOSEMU</a></li>

<li><a href="PikeOS" title="PikeOS">PikeOS</a></li>

<li><a href="SheepShaver" title="SheepShaver">SheepShaver</a></li>

<li><a href="Windows_on_Windows" title="Windows on Windows">Windows on Windows</a>

<ul><li><a href="Virtual_DOS_machine" title="Virtual DOS machine">Virtual DOS machine</a></li></ul></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Independent</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Bhyve" title="Bhyve">bhyve</a></li>

<li><a href="Microsoft_Virtual_Server" title="Microsoft Virtual Server">Microsoft Virtual Server</a></li>

<li><a href="Parallels_Workstation" title="Parallels Workstation">Parallels Workstation</a> (<a href="Parallels_Workstation_Extreme" title="Parallels Workstation Extreme">Extreme</a>)</li>

<li><a href="Parallels_Desktop_for_Mac" title="Parallels Desktop for Mac">Parallels Desktop for Mac</a></li>

<li><a href="Parallels_Server_for_Mac" class="mw-redirect" title="Parallels Server for Mac">Parallels Server for Mac</a></li>

<li><a href="PearPC" title="PearPC">PearPC</a></li>

<li><a href="VirtualBox" title="VirtualBox">VirtualBox</a></li>

<li><a href="Virtual_Iron" title="Virtual Iron">Virtual Iron</a></li>

<li><a href="Virtual_PC" title="Virtual PC">Virtual PC</a></li>

<li><a href="VMware_Fusion" title="VMware Fusion">VMware Fusion</a></li>

<li><a href="VMware_Server" title="VMware Server">VMware Server</a></li>

<li><a href="VMware_Workstation" title="VMware Workstation">VMware Workstation</a> (<a href="VMware_Workstation_Player" title="VMware Workstation Player">Player</a>)</li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Tools</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Ganeti" title="Ganeti">Ganeti</a></li>

<li><a href="System_Center_Virtual_Machine_Manager" title="System Center Virtual Machine Manager">System Center Virtual Machine Manager</a></li>

<li><a href="Virt-manager" title="Virt-manager">Virt-manager</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="OS-level_virtualization" title="OS-level virtualization">Operating<br>system</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">OS containers</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="FreeBSD_jail" title="FreeBSD jail">FreeBSD jail</a></li>

<li>iCore Virtual Accounts</li>

<li><a href="Linux-VServer" title="Linux-VServer">Linux-VServer</a></li>

<li><a href="LXC" title="LXC">Linux Containers</a></li>

<li><a href="OpenVZ" title="OpenVZ">OpenVZ</a></li>

<li><a href="Solaris_Containers" title="Solaris Containers">Solaris Containers</a></li>

<li><a href="Virtuozzo_(company)#Software" title="Virtuozzo (company)">Virtuozzo</a></li>

<li><a href="Workload_Partitions" title="Workload Partitions">Workload Partitions</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Application containers</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Docker_(software)" title="Docker (software)">Docker</a></li>

<li><a href="Podman" title="Podman">Podman</a></li>

<li><a href="Lmctfy" title="Lmctfy">lmctfy</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Virtual kernel architectures</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Rump_kernel" title="Rump kernel">Rump kernel</a></li>

<li><a href="User-mode_Linux" title="User-mode Linux">User-mode Linux</a></li>

<li><a href="Vkernel" title="Vkernel">vkernel</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related kernel features</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Solaris_Containers#Branded_zones" title="Solaris Containers">BrandZ</a></li>

<li><a href="Cgroups" title="Cgroups">cgroups</a></li>

<li><a href="Chroot" title="Chroot">chroot</a></li>

<li><a href="Linux_namespaces" title="Linux namespaces">namespaces</a></li>

<li><a href="Seccomp" title="Seccomp">seccomp</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Orchestration</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Amazon_Web_Services" title="Amazon Web Services">Amazon ECS</a></li>

<li><a href="Kubernetes" title="Kubernetes">Kubernetes</a></li>

<li><a href="OpenShift" title="OpenShift">OpenShift</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Desktop_virtualization" title="Desktop virtualization">Desktop</a></th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Citrix_Virtual_Apps" title="Citrix Virtual Apps">Citrix Virtual Apps</a></li>

<li><a href="Citrix_Virtual_Desktops" title="Citrix Virtual Desktops">Citrix Virtual Desktops</a></li>

<li><a href="Remote_Desktop_Services" title="Remote Desktop Services">Remote Desktop Services</a></li>

<li><a href="VMware_Horizon" class="mw-redirect" title="VMware Horizon">VMware Horizon</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Application_virtualization" title="Application virtualization">Application</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Ceedo" title="Ceedo">Ceedo</a></li>

<li><a href="Citrix_Virtual_Apps" title="Citrix Virtual Apps">Citrix Virtual Apps</a></li>

<li><a href="Dalvik_(software)" title="Dalvik (software)">Dalvik</a></li>

<li><a href="InstallFree" title="InstallFree">InstallFree</a></li>

<li><a href="Microsoft_App-V" title="Microsoft App-V">Microsoft App-V</a></li>

<li><a href="Remote_Desktop_Services" title="Remote Desktop Services">Remote Desktop Services</a></li>

<li><a href="Symantec_Workspace_Virtualization" title="Symantec Workspace Virtualization">Symantec Workspace Virtualization</a></li>

<li><a href="Turbo_(software)" title="Turbo (software)">Turbo</a></li>

<li><a href="VMware_ThinApp" title="VMware ThinApp">VMware ThinApp</a></li>

<li><a href="ZeroVM" title="ZeroVM">ZeroVM</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Network_virtualization" title="Network virtualization">Network</a></th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Distributed_Overlay_Virtual_Ethernet" title="Distributed Overlay Virtual Ethernet">Distributed Overlay Virtual Ethernet</a> (DOVE)</li>

<li><a href="Ethernet_VPN" title="Ethernet VPN">Ethernet VPN</a> (EVPN)</li>

<li><a href="Network_Virtualization_using_Generic_Routing_Encapsulation" title="Network Virtualization using Generic Routing Encapsulation">NVGRE</a></li>

<li><a href="Open_vSwitch" title="Open vSwitch">Open vSwitch</a></li>

<li><a href="Virtual_security_switch" title="Virtual security switch">Virtual security switch</a></li>

<li><a href="Virtual_Extensible_LAN" title="Virtual Extensible LAN">Virtual Extensible LAN</a> (VXLAN)</li>

<li><a href="Generic_Network_Virtualization_Encapsulation" title="Generic Network Virtualization Encapsulation">Generic Network Virtualization Encapsulation</a> (GENEVE)</li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">See also</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="BlueStacks" title="BlueStacks">BlueStacks</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>See also: <a href="List_of_emulators" title="List of emulators">List of emulators</a>, <a href="List_of_computer_system_emulators" title="List of computer system emulators">List of computer system emulators</a></div></td></tr></tbody></table></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-label="Navbox599" style="padding:3px"><table class="nowraplinks hlist navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Authority control databases: National </th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><span class="rt-commentedText tooltip tooltip-dotted" title="virtualizace (počítače)"><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph570207&CON_LNG=ENG">Czech Republic</a></span></span></li></ul></div></td></tr></tbody></table></div>

<p><br>

Chapter: 2

Hypervisor Used: VirtualBox

VM Computer Name: UbuntuVM1

Operating System: Ubuntu Desktop 22.04 LTS

Notes: Used for practicing Linux networking tools. Firefox used to verify internet access. No Ubuntu Pro features enabled.

</p></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-03" href="https://en.wikipedia.org/wiki/?title=Virtualization&oldid=1298582304">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>